Wearable device and method of operating the same

ABSTRACT

A wearable device includes a display; a sensor configured to obtain a biometric information of a user; a memory configured to store at least one instruction; and at least one processor configured to execute the at least one instruction to: based on an event related to executing an application, identify execution of biometric authentication associated with the application; based on the identification, display a message indicating information corresponding to the biometric authentication to be performed in the wearable device; obtain, by the sensor, the biometric information of the user wearing the wearable device; identify authority using the obtained biometric information and registered biometric information stored in the memory; and display, by the display, a screen associated with the executed application based on the identified authority.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of application Ser. No. 14/812,436,filed Jul. 29, 2015, which is based upon and claims priority from KoreanPatent Application No. 10-2014-0098645, filed on Jul. 31, 2014, in theKorean Intellectual Property Office, the disclosure of which isincorporated herein by reference in its entirety.

BACKGROUND

1. Field

Apparatuses and methods consistent with exemplary embodiments relate toa wearable device and a method of operating the same.

2. Description of the Related Art

Wearable devices, such as smart watches, smart glasses, etc., havebecome popular. A wearable device may capture an image of a portion orall of a user's body and may identify a user wearing the wearable devicebased on the captured image. For example, the smart watch may be worn ona user's wrist to capture an image of the user's veins in order toidentify a user. The smart watch may also capture an image of the user'seye in order to identify a user.

Accordingly, a wearable device may allow a user to use the wearabledevice more conveniently and easily according to a particular usageenvironment of the wearable device.

SUMMARY

One or more exemplary embodiments provide a usage environment suitablefor a user of a wearable device.

Additional aspects will be set forth in part in the description whichfollows and, in part, will be apparent from the description, or may belearned by practice of exemplary embodiments.

According to an aspect of an exemplary embodiment, there is provided awearable device including a sensor configured to capture a vein image ofa user; and a processor configured to in response to a function or anapplication being selected by the user, control the sensor to capturethe vein image of the user wearing the wearable device; identify theuser by comparing the captured vein image with at least one registeredvein image; and in response to determining that the identified user hasan execution authority for the selected function or application, executethe function or the application.

The function or the application may be a function or an application inwhich a user is predesignated.

According to an aspect of another exemplary embodiment, there isprovided a wearable device including a sensor configured to capture avein image of a user; and a processor configured to in response todetermining that the user is wearing the wearable device, control thesensor to capture the vein image of the user; identify the user bycomparing the captured vein image with at least one registered veinimage; and change a setting of the wearable device according to settinginformation that is registered with respect to the identified user.

The wearable device may further include a temperature sensor configuredto measure a temperature of the user, wherein the processor is furtherconfigured to, in response to determining that the measured temperaturecorresponds to a temperature of a body, determine that the identifieduser is wearing the wearable device.

The wearable device may further include a pulse sensor configured tomeasure a pulse of the user, wherein the processor is further configuredto, in response to determining that the measured pulse corresponds to apulse of a body, determine that the identified user is wearing thewearable device.

The processor may be further configured to perform a wirelesscommunication connection according to a wireless communication settingthat is registered with respect to the identified user.

The processor may be further configured to change the setting of thewearable device by using a brightness and a ringtone that is registeredwith respect to the identified user.

According to an aspect of another exemplary embodiment, there isprovided a wearable device including a sensor configured to capture avein image of a user; a display configured to display a contact list;and a processor configured to: in response to a contact function beingselected, control the sensor to capture the vein image of the user;identify the user by comparing the captured vein image with at least oneregistered vein image; and control the display to display the contactlist that is registered with respect to the identified user.

According to an aspect of another exemplary embodiment, there isprovided a wearable device including a sensor configured to capture avein image of a user; a display configured to display a music list; anda processor configured to: in response to a music player being selected,control the sensor to capture the vein image of the user; identify theuser by comparing the captured vein image with at least one registeredvein image; and control the display unit to display the music listregistered with respect to the identified user.

According to an aspect of another exemplary embodiment, there isprovided a wearable device including a processor configured to: inresponse to the user selecting an SNS function, control the sensor tocapture the vein image of the user; identify the user by comparing thecaptured vein image with at least one registered vein image; and log into the SNS by inputting authentication information that is registeredwith respect to the identified user.

According to an aspect of another exemplary embodiment, there isprovided a method of operating a wearable device, the method includingregistering an execution authority of a user and a vein image of theuser, for each user from among the at least one user; in response to afunction or an application being selected by the user, capturing a veinimage of the user wearing the wearable device; and identifying the userby comparing the captured vein image with the at least one registeredvein image; and in response to determining that the identified user hasthe execution authority for the selected function or application,executing the function or the application.

The function or the application may be a function or an application inwhich a user is predesignated.

According to an aspect of another exemplary embodiment, there isprovided a method of operating a wearable device, the method includingregistering setting information of a user and a vein image of the user,for each user from among the at least one user; in response todetermining that the user is wearing the wearable device, capturing avein image of the user; identifying the user by comparing the capturedvein image with the at least one registered vein image; and changing asetting of the wearable device by using the setting information of theidentified user.

The capturing may further include capturing the vein image of the userin response to a temperature of the user's body being sensed.

The registering may further include registering a wireless communicationsetting with respect to each user, and the changing further comprisesperforming a wireless communication connection according to the wirelesscommunication setting with respect to the identified user.

The registering may further include registering at least one of abrightness and a ringtone with respect to each user, and the changing ofthe setting further comprises changing the setting of the wearabledevice by using at least one of the brightness and the ringtoneregistered with respect to the identified user.

According to an aspect of another exemplary embodiment, there isprovided a method of operating a wearable device, the method includingregistering a contact list of a user and a vein image of the user, foreach user from among the at least one user; in response to the userselecting a contact function, capturing a vein image of the user wearingthe wearable device; identifying the user wearing the wearable device bycomparing the captured vein image with the at least one registered veinimage; and displaying the contact list of the identified user.

According to an aspect of another exemplary embodiment, there isprovided a method of operating a wearable device, the method includingregistering a music list of a user and a vein image of the user, foreach user from among the at least one user; in response to the userselecting a music player, capturing a vein image of the user wearing thewearable device; identifying the user wearing the wearable device bycomparing the captured vein image with the at least one registered veinimage; and displaying the music list of the identified user.

According to an aspect of another exemplary embodiment, there isprovided a method of operating a wearable device, the method includingregistering SNS authentication information of a user and a vein image ofthe user, for each user from among the at least one user; in response tothe user selecting an SNS function, capturing a vein image of the userwearing the wearable device; identifying the user wearing the wearabledevice by comparing the captured vein image with the at least oneregistered vein image; and logging in to the SNS by inputting the SNSauthentication information of the identified user.

According to an aspect of another exemplary embodiment, there isprovided a wearable device including a sensor configured to capture animage of a portion of a user's body; a processor configured to: comparethe captured image to a database comprising at least one registeredimage; determine an identity of the user based on a result of thecomparison; determine an execution authority of the user based on theidentity of the user; and in response to determining that the user hasexecution authority for performing at least one of a function and anapplication, control the wearable device to perform the function or theapplication.

The portion of the user's body that is captured may include at least oneof the user's vein, the user's eye, and the user's finger.

The at least one function may include providing an advertisement relatedto interest information based on the identity of the user.

The wearable device may further include a display configured to displaymessages to the user, and wherein the processor is further configuredto, in response to determining that the user does not have executionauthority, display a message to the user indicating that the user doesnot have execution authority to perform the function or the application.

The at least one function may include performing authentication with acredit card according to the identity of the user.

BRIEF DESCRIPTION OF THE DRAWINGS

These and/or other aspects will become apparent and more readilyappreciated from the following description of the exemplary embodiments,taken in conjunction with the accompanying drawings in which:

FIG. 1 is a diagram illustrating a wearable device that performs variousfunctions through vein authentication, according to an exemplaryembodiment;

FIG. 2 is a block diagram illustrating a wearable device according to anexemplary embodiment;

FIG. 3 is a block diagram illustrating a wearable device according to anexemplary embodiment;

FIG. 4 is a flowchart illustrating a method by which a wearable devicechanges a setting thereof, according to an exemplary embodiment;

FIG. 5 is a diagram illustrating a process by which a wearable devicechanges a setting thereof, according to an exemplary embodiment;

FIG. 6 is a flowchart illustrating a method by which a wearable devicedisplays a contact list, according to an exemplary embodiment;

FIG. 7 is a diagram illustrating a process by which a wearable deviceprovides a contact list, according to an exemplary embodiment;

FIG. 8 is a flowchart illustrating a method by which a wearable deviceprovides a music list, according to an exemplary embodiment;

FIG. 9 is a diagram illustrating a process by which a wearable deviceprovides a music list, according to an exemplary embodiment;

FIG. 10 is a diagram illustrating a timing of performing veinauthentication, according to an exemplary embodiment;

FIG. 11 is a diagram illustrating that a wearable device provides amusic list with respect to an identified user, according to an exemplaryembodiment;

FIG. 12 is a flowchart illustrating a method by which a wearable devicelogs in an SNS, according to an exemplary embodiment;

FIG. 13 is a diagram illustrating a process by which a wearable devicedisplays automatically performs login, according to an exemplaryembodiment;

FIG. 14 is a diagram illustrating a process by which a wearable deviceautomatically performs login, according to an exemplary embodiment;

FIG. 15 is a flowchart illustrating a method by which a wearable deviceselectively executes a function or an application, according to anexemplary embodiment;

FIG. 16 is a flowchart illustrating a method by which a wearable deviceautomatically performs payment with a credit card, according to anexemplary embodiment;

FIG. 17 is a diagram illustrating a process by which a wearable deviceperforms payment by using registered credit card information, accordingto an exemplary embodiment;

FIG. 18 is a diagram illustrating a payment screen according to anexemplary embodiment;

FIG. 19 is a flowchart illustrating a method by which a wearable deviceprovides an advertisement, according to an exemplary embodiment;

FIG. 20 is a diagram illustrating a process by which a wearable deviceregisters interest information, according to one or more exemplaryembodiment;

FIG. 21 is a flowchart illustrating a method by which a wearable devicetransmits data, according to an exemplary embodiment;

FIG. 22 is a flowchart illustrating a method by which a wearable deviceis connected to other devices, according to an exemplary embodiment;

FIG. 23 is a diagram illustrating a process by which a wearable devicedisplays a vein authentication procedure, according to an exemplaryembodiment;

FIG. 24 is a diagram illustrating a process by which a wearable devicedisplays an authentication region, according to an exemplary embodiment;

FIG. 25 is a diagram illustrating a sensor arrangement of a wearabledevice according to an exemplary embodiment; and

FIG. 26 is a diagram illustrating a sensor arrangement of a wearabledevice according to an exemplary embodiment.

DETAILED DESCRIPTION

Reference will now be made in detail to exemplary embodiments, examplesof which are illustrated in the accompanying drawings, in which likereference numerals refer to like elements throughout. In this regard,the present exemplary embodiments may have different forms and shouldnot be construed as being limited to the descriptions set forth herein.The exemplary embodiments are merely described below, by referring tothe figures, to explain exemplary aspects of the present disclosure. Asused herein, the term “and/or” includes any and all combinations of oneor more of the associated listed items. Expressions such as “at leastone of,” when preceding a list of elements, modify the entire list ofelements and do not modify the individual elements of the list.

It should be understood that, although the terms “first”, “second”,“third”, etc. may be used herein to describe various elements, theseelements should not be limited by these terms. These terms are only usedto distinguish one element from another. For example, a first elementmay be referred to as a second element, and similarly, a second elementmay be referred to as a first element.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to limit the inventive concepts. Asused herein, the singular forms “a,” “an,” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It should be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

FIG. 1 is a diagram illustrating a wearable device 100 that performsvarious functions through vein authentication, according to an exemplaryembodiment.

The wearable device 100 may include a sensor 110 and a display unit 120(e.g., display). The sensor 110 may perform a variety of functions suchas capturing a vein image of a user or sensing a body temperature of theuser. The display unit 120 may display at least one of an image, anicon, a clock, a video, etc.

The wearable device 100 may capture an image of the veins of the user toacquire the vein image. The wearable device 100 may capture the veinimage in response to a predetermined situation occurring. For example,the wearable device 100 may sense a particular situation, such as a userputting on or taking off the wearable device 100, a user's performing aparticular operation, a specific function being executed, or aparticular application being executed, etc.

According to an exemplary embodiment, the wearable device 100 maycapture the vein image when the user wears the wearable device 100. Forexample, the wearable device 100 may determine whether the user iscurrently wearing the wearable device 100. Further, the wearable device100 may generate an event at the time when the user wears the wearabledevice 100. An event may refer to a predetermined situation that arisesin which the wearable device responds by performing a predeterminedaction. For example, when the wearable device 100 determines that theuser is currently wearing the device, the wearable device 100 generatesan event and the wearable device 100 may capture the vein image.According to an exemplary embodiment, the wearable device 100 maydetermine through various sensors whether the user wears the wearabledevice 100. Then, the sensor may generate the event at the time when theuser wears the wearable device 100.

In another exemplary embodiment, the wearable device 100 may capture thevein image when a function or a program that requires a user's authorityis selected. For example, the wearable device 100 may generate an eventat the time when a particular function or program is executed. When theevent is generated, the wearable device 100 may capture the vein image.The function or the program that requires the user's authority may bepreset by the user. In addition, a specific function or a specificprogram may request the user's authority. The executing of the functionmay be the wearable device 100 processing data, changing contentsdisplayed on the display unit 120, or changing a plurality of pieces ofset data. The program may a music player, a video player, a game, oranother application installed on the wearable device 100.

According to an exemplary embodiment, the wearable device 100 mayperform vein authentication by comparing the captured vein image with aregistered vein image stored in memory or stored in an external server.The performing of the vein authentication may include determiningwhether any of the registered vein images matches the captured veinimage.

According to an exemplary embodiment, when a plurality of registeredvein images are provided, the wearable device 100 may sequentiallycompare the captured vein image with each of the registered vein imagesto select the registered vein image that matches the captured veinimage. The matching of the captured vein image to the registered veinimage may represent that the captured vein image matches the registeredvein image in a set ratio or more by comparing the captured vein imagewith the registered vein image. In other words, there may be an errorvalue attached to the matching of the captured vein image to theregistered vein image, and when the error is a set critical value orless, the wearable device 100 may determine that the captured vein imagematches the registered vein image.

According to an exemplary embodiment, the wearable device 100 mayexecute the function or the application without a separate user input byusing data registered with respect to an identified user. Therefore,when a function or a program that requires user authentication isselected, the wearable device 100 may receive no separate input from theuser and may automatically capture the vein image of the user to performthe user authentication. In other words, when the user has authority touse the function or the program, i.e., the user has a matching veinstructure, the selected function or the selected program may beautomatically executed without any input from the user. On the otherhand, when the user has no authority to use the function or the program,i.e., the user does not have a matching vein structure, the selectedfunction or the selected program may not be executed.

According to an exemplary embodiment, the wearable device 100 mayexecute various functions by using authentication. For example, thewearable device 100 may provide a music list according to musicpreferred by an authenticated user. The wearable device 100 may providean advertisement or information in which the authenticated user isinterested. The wearable device 100 may update a setting thereofaccording to the authenticated user. The wearable device 100 may providea contact list of the authenticated user. The wearable device 100 mayperform automatic login to an SNS accessed by the user. The wearabledevice 100 may be configured to only transmit data when theauthenticated user has authority to transmit data. The wearable device100 may attempt to connect to other devices by using informationregistered by the authenticated user. The wearable device 100 mayattempt payment with a credit card by using information registered bythe authenticated user. Functions provided by the wearable device 100 tothe user will be described in detail below with reference to thedrawings.

FIG. 2 is a block diagram of a wearable device 100 according to anexemplary embodiment. Referring to FIG. 2, the wearable device 100 mayinclude a sensor 110 and a processor 140. According to an exemplaryembodiment, the wearable device may include a controller that mayinclude the processor 140.

The sensor 110 may capture a vein image. The sensor 110 may include alight source and a camera. The light source may emit an infrared ray,etc., and the camera may capture the vein image. While the infrared rayis emitted from the light source, the camera may capture an image of theback of user's hand, or another part of the body, to acquire the veinimage. Since a portion in which a vein is disposed has high infraredreflectivity compared to other portions of the back of hand, the cameramay capture a reflected infrared ray to capture the vein image.

According to an exemplary embodiment, the sensor 110 may capture animage of biological information capable of identifying the user. Theidentifying the user may include determining who is the user currentlywearing the wearable device 100, or who is the user from among aplurality of registered users, which is wearing the wearable device 100.For example, the sensor 110 may capture an image of biologicalinformation on a user's vein, iris, or finger, etc. As another example,the sensor 110 may capture vein images of both the user's hands. As yetanother example, the sensor 110 may capture vein images of the back ofthe user's hand and the palm of the user's hand. According to anexemplary embodiment, the sensor 110 may capture iris images of both ofa user's eyes.

In response to a function or an application, which requiresauthentication, being selected, the processor 140 may control the sensor110 to capture the vein image of the user wearing the wearable device100. The selecting the function or the application may include a userselecting the function or the application by using an input unit (e.g.,inputter) in order to execute the function or the application.

The processor 140 may then identify the user by comparing the capturedvein image with a registered vein image from among a plurality ofregistered vein images. The processor 140 may identify the usercurrently wearing the wearable device 100. The identifying of the usermay include determining any user who wears the wearable device 100 fromamong a plurality of users. In other words, the identifying of the usermay include determining a registered vein image from among a pluralityof registered vein images, which matches the vein image of the usercurrently wearing the wearable device 100. The comparing of the veinimages may represent comparing shapes, structures, and/or thicknesses ofveins included in the captured vein image and the registered veinimages.

According to an exemplary embodiment, the processor may execute afunction of an application if it is determined that the user hasexecution authority. For example, the processor 140 may identify theuser and may determine whether the identified user has the executionauthority. A user with authority to execute each particular function orapplication may be predetermined. If a user has no execution authority,the processor 140 may provide feedback indicating that the user has noexecution authority.

According to an exemplary embodiment, the processor 140 may provide dataregistered with respect to the identified user. For example, theprocessor 140 may store different contact lists of each user. When theuser selects a function for providing a contact list, the processor 140may identify the user through the vein authentication and may providethe contact list registered with respect to the identified user.

FIG. 3 is a block diagram of a wearable device 100 according to anexemplary embodiment. Referring to FIG. 3, the wearable device 100 mayinclude a sensor 110, a display unit 120, a memory 130, and a processor140.

The memory 130 may store biological information which may be used toidentify a user. For example, the memory 130 may store biologicalinformation about a user's vein, iris, pulse, or finger. The memory 130may store vein images of both of a user's hands. The memory 130 maystore vein images of the back of a user's hand and the palm of a user'shand. The memory 130 may store iris images of both of a user's eyes.

According to an exemplary embodiment, the memory 130 may store a user'sdata. For example the memory 130 may store a user's music list orcontact list, and setting information or interest information about theuser. The setting information may include information for wirelesscommunication such as Wi-Fi, 3G, or LTE. In addition, the settinginformation may include notification information such as a vibration ora ringtone.

The memory 130 may also store user authentication information. Forexample, the memory 130 may store credit card information, SNSinformation, etc. The credit card information may include a credit cardnumber, a credit card expiration date, a password, or the like. The SNSinformation may include an SNS address, an identification (ID), apassword, or the like.

The display unit 120 may display a screen for controlling an electronicdevice through control of a processor 140. The display unit 120 may be atouch panel that receives an input from the user (e.g., touchscreen).

According to an exemplary embodiment, the display unit 120 may displayan authentication process. For example, the display unit 120 may displaya message while authentication is being performed. In addition, thedisplay unit 120 may display a captured vein image.

FIG. 4 is a flowchart of a method by which a wearable device 100 changesa setting thereof, according to an exemplary embodiment. Referring toFIG. 4, the wearable device 100 may update a setting of a user throughvein authentication.

In operation 410, the wearable device 100 may register settinginformation about a user and a vein image of the user. The settinginformation may be information for wireless communication, notificationinformation, or the like. The wearable device 100 may receive thesetting information from the user and may register the received settinginformation. For example, the wearable device 100 may receiveinformation from the user about whether the wearable device 100 performswireless communication connection through Wi-Fi or LTE. In addition, thewearable device 100 may receive a vibration magnitude, a ringtonevolume, and/or a ringtone type from the user. The wearable device 100may also capture and store a vein image and may store the settinginformation inputted by the user.

In operation 420, the wearable device 100 may capture a vein image ofthe user when the user is wearing the wearable device 100. The wearabledevice 100 may sense whether a user is wearing the wearable device 100.When it is determined that a user is wearing the wearable device 100,the wearable device 100 may capture the vein image of the user wearingthe wearable device 100.

According to an exemplary embodiment, the wearable device 100 may sensewhether a user is wearing the wearable device 100 based on a buckle(e.g., strap), a body temperature sensor, a pulse sensor, a proximitysensor, etc.; however, exemplary embodiments are not limited to thesesensing methods.

The buckle may represent a portion that fixes the wearable device 100 toa user's body. When the buckle is fastened to the wearable device 100,the wearable device 100 may determine that a user is wearing thewearable device 100.

According to another exemplary embodiment, when a body temperature ofthe user is sensed by the body temperature sensor, the wearable device100 may determine that a user is wearing the wearable device 100. Thebody temperature sensor may be disposed on a contact portion of thewearable device, i.e., the portion that contacts the user when the userwears the wearable device 100.

According to another exemplary embodiment, when a pulse of the user issensed by the pulse sensor, the wearable device 100 may determine that auser is wearing the wearable device 100. The pulse sensor may bedisposed on a portion of the wearable device that contacts the user whenthe user wears the wearable device 100. For example, in the case of asmart watch, the pulse sensor may be disposed on a portion that comesinto contact with a lower portion of a user's wrist.

According to another exemplary embodiment, the wearable device 100 maydetermine through a proximity sensor whether a user is wearing thewearable device 100. The proximity sensor may be disposed on the contactportion when the user is wearing the wearable device 100. For example,in the case of a smart watch, the proximity sensor may be disposed belowthe display unit 120 to measure a distance between the smart watch andthe user's wrist.

In operation 430, the wearable device 100 may identify the user bycomparing the captured vein image with a registered vein image. Thewearable device 100 may search for a vein image from among a pluralityof vein images stored in the memory 130 that matches the captured veinimage. When the wearable device 100 determines that the captured veinimage and the registered vein image match each other by a predeterminedratio or more, in terms of a structure, or the like, the wearable device100 may determine that the captured vein image and the registered veinimage match each other. The wearable device 100 may then identify whichuser is wearing the wearable device 100 by determining which usercorresponds to the matching registered vein image.

In operation 440, the wearable device 100 may change a setting of thewearable device 100 by using the setting information of the user. Forexample, the wearable device 100 may use setting information registeredof the user that corresponds to the registered vein image that matchesthe captured vein image. In other words, the wearable device 100 may usesetting information registered with respect to the identified user. Thesetting information may include information that determines a state ofthe wearable device 100. The wearable device 100 may change its statebased on the setting information of the identified user. For example,the wearable device 100 may confirm music registered with respect to theidentified user and may change a ringtone to the confirmed music. Inaddition, the wearable device 100 may confirm a wireless connection typeregistered with respect to the identified user and may change theconfirmed wireless connection type to Wi-Fi or LTE accordingly.

FIG. 5 is a diagram illustrating a process by which a wearable device100 changes a setting thereof, according to an exemplary embodiment.Referring to FIG. 5, when a user wears the wearable device 100, thewearable device 100 may identify the user wearing the wearable device100. The wearable device 100 may update a setting thereof by usingsetting information of the identified user.

For example, when a first user wears the wearable device 100, thewearable device 100 may compare a captured vein image with first andsecond vein images. If the captured vein image matches the first veinimage, the wearable device 100 may determine that the first user wearsthe wearable device 100. The wearable device 100 may update the settingthereof by using first setting information registered with respect tothe first user.

The memory 130 of the wearable device 100 may store the first settinginformation of the first user and second setting information of a seconduser. The first setting information may be setting informationregistered with respect to the first user. The second settinginformation may be setting information registered with respect to thesecond user.

In addition, the memory 130 may store first and second vein images ofthe first and second users. The first vein image may be a vein image ofthe first user. The second vein image may be a vein image of the seconduser.

The first setting information may indicate that LTE is set to an ONstate, Wi-Fi is set to an OFF state, GPS is set to an OFF state,Bluetooth is set to an ON state, NFC is set to an ON state, brightnessis set to 50%, and a mode is set to a vibration mode. For example, whenthe first user is wearing the wearable device 100, the wearable device100 may perform wireless communication connection by using the LTE andmay disconnect a Wi-Fi connection.

The second setting information may indicate that the LTE is set to anOFF state, the Wi-Fi is set to an ON state, the GPS is set to an OFFstate, the Bluetooth is set to an ON state, the NFC is set to an OFFstate, the brightness is set to an automatic mode, and the mode is setto a ringtone mode. For example, when the second user wears the wearabledevice 100, the wearable device 100 may perform the wirelesscommunication connection by using the Wi-Fi and may disconnect a LTEconnection.

The storage of the first setting information, the second settinginformation, and the first and second vein images with respect to thefirst and the second users has been described with reference to FIG. 5,but the number of the stored users is not limited, and a plurality ofpieces of setting information and vein images with respect to three ormore users may be stored in the memory 130. Furthermore, the settinginformation is not limited to these pieces of information.

FIG. 6 is a flowchart of a method by which a wearable device 100displays a contact list, according to an exemplary embodiment. Referringto FIG. 6, when a contact is selected, the wearable device 100 mayprovide a contact list of an identified user.

In operation 610, the wearable device 100 may register the contact listof a user and a vein image of the user. The contact list may include acellular phone number, a home phone number, an office phone number, afax number, etc.

In operation 620, when the contact function is selected, the wearabledevice 100 may capture a vein image of the user wearing the wearabledevice 100. The selecting of the contact function may represent that theuser executes a phone function through an input device of the wearabledevice 100 or selects a contact icon. In other words, the selecting thecontact function may include all cases that the wearable device 100displays the contact list. The input device may be a device such as atouch panel, a touchscreen, or a mouse. When the contact list isselected, the wearable device 100 may generate an event, which maycontrol the sensor 110 to capture the vein image.

Since the wearable device 100 may store different contact lists for eachuser, it is necessary to provide the contact list registered withrespect to the user currently wearing the wearable device 100.Therefore, the wearable device 100 may control the sensor 110 to capturethe vein image in order to identify the user wearing the wearable device100.

In operation 630, the wearable device 100 may identify the user wearingthe wearable device 100 by comparing the captured vein image with theregistered vein images.

In operation 640, the wearable device 100 may display the contact listcorresponding to the identified user on the display unit 120. Thewearable device 100 may control the display unit 120 so as to displaythe contact list of the identified user.

Since the wearable device 100 provides the contact list to the userthrough vein authentication, although many users use the wearable device100, only the user currently wearing the device may view his or her owncontact list. Therefore, the wearable device 100 may protect personalinformation.

FIG. 7 is a diagram illustrating a process by which a wearable device100 provides a contact list, according to an exemplary embodiment.Referring to FIG. 7, when a contact function is selected, the wearabledevice 100 may provide a contact list registered with respect to theuser that is wearing the wearable device 100.

For example, when a first user is wearing the wearable device 100 andselects the contact, the wearable device 100 may perform veinauthentication. During this process, the wearable device 100 may comparea captured vein image with registered first and second vein images. Ifthe captured vein image matches the first vein image, the wearabledevice 100 may determine that the first user wears the wearable device100. The wearable device 100 may provide a first contact list registeredwith respect to the first user.

The memory 130 of the wearable device 100 may store vein images of firstand second users. The first vein image may be a vein image of the firstuser. The second vein image may be a vein image of the second user. Inaddition, the memory 130 may store first and second contact lists. Thefirst contact list may include contacts registered by the first user.The second contact list may include contacts registered by the seconduser.

As an example, illustrated in FIG. 7, the first contact list may includephone numbers of Tom, Jack, and Billy. The second contact list mayinclude phone numbers of Irene, Jinhee, and Donghee.

The storage of the first and second contact lists and the first andsecond vein images with respect to the first and second users has beendescribed with reference to FIG. 7, but the number of the stored usersis not limited, and contact lists and vein images of three or more usersmay be stored in the memory 130.

FIG. 8 is a flowchart of a method by which a wearable device 100provides a music list, according to an exemplary embodiment. Referringto FIG. 8, when a music player is selected, the wearable device 100 mayprovide a music list registered by an identified user.

In operation 810, the wearable device 100 may register the music list ofthe user and a vein image of the user. The music list may include songsregistered by the user.

In operation 820, when the music player is selected, the wearable device100 may capture a vein image of the user wearing the wearable device100. The selecting of the music player may represent that the userexecutes the music player through the input device of the wearabledevice 100. The music player may represent any programs that play asong.

Since the wearable device 100 stores different music lists for eachuser, it is necessary to provide the music list registered with respectto the user wearing the wearable device 100. Therefore, the wearabledevice 100 may control the sensor 110 to capture the vein image in orderto identify the user wearing the wearable device 100.

In operation 830, the wearable device 100 may identify the user wearingthe wearable device 100 by comparing the captured vein image with theregistered vein images.

In operation 840, the wearable device 100 may display the music list ofthe identified user on the display unit 120. The wearable device 100 maycontrol the display unit 120 so as to display the music list of theidentified user.

Since the wearable device 100 provides the music list to the userthrough vein authentication, the wearable device 100 may provide musicregistered by the user wearing the wearable device 100 even in theabsence of a separate input.

FIG. 9 is a diagram illustrating a process by which a wearable device100 provides a music list, according to an exemplary embodiment.Referring to FIG. 9, when a music player is selected, the wearabledevice 100 may provide a music list registered with respect to anidentified user.

For example, when a first user wears the wearable device 100 and selectsthe music player, the wearable device 100 may perform veinauthentication. In other words, the wearable device 100 may compare acaptured vein image with registered first and second vein images. If thecaptured vein image matches the first vein image, the wearable device100 may determine that the first user wears the wearable device 100. Thewearable device 100 may then provide a first music list registered withrespect to the first user.

According to an exemplary embodiment, the memory 130 of the wearabledevice 100 may store vein images of first and second users. The firstvein image may be a vein image of the first user. The second vein imagemay be a vein image of the second user.

In addition, the memory 130 may store first and second music lists. Thefirst music list may include songs registered by the first user. Thesecond music list may include songs registered by the second user. As anexample, the first music list may include songs such as You Are NotAlone, I'll Be There, and Beat it, and the second music list may includesongs such as Stronger, Because Of You, and Baby it's Cold Outside.

FIG. 10 is a diagram for illustrating the timing of performing veinauthentication. Referring to FIG. 10, a wearable device 100 may performvein authentication at the time when a music player is executed. Morespecifically, the wearable device 100 may perform the veinauthentication before the user selects and executes the music player.The wearable device 100 may execute the music player after the veinauthentication is completed.

FIG. 10 illustrates that a photograph icon 1010, a music icon 1020, avideo icon 1030, and a document icon 1040 are disposed in the wearabledevice 100. The photograph icon 1010, the music icon 1020, the videoicon 1030, and the document icon 1040 may each represent a program or anapplication that executes each of the respective functions. When thephotograph icon 1010 is selected, the wearable device 100 may execute afunction of displaying photographs. When the music icon 1020 isselected, the wearable device 100 may execute a function of playing asong. When the video icon 1030 is selected, the wearable device 100 mayexecute a function of playing a video. When the document icon 1040 isselected, the wearable device 100 may execute a program of performing adocument operation.

As illustrated in FIG. 10, when the user touches the music icon 1020,the wearable device 100 may sense a touch input as an event and mayperform the vein authentication. The wearable device 100 may control thesensor 110 to capture a vein image of the user. The wearable device 100may identify the user by comparing the captured vein image withregistered first and second vein images.

FIG. 11 is a diagram illustrating that a wearable device 100 provides amusic list with respect to an identified user, according to an exemplaryembodiment. If the wearable device 100 determines that the first user ofthe FIG. 9 is wearing the wearable device 100, then it may provide afirst music list of registered music lists. Therefore, the wearabledevice 100 may display songs such as You Are Not Alone, I'll Be There,and Beat it, on the display unit 120.

FIG. 12 is a flowchart of a method by which a wearable device 100 logsin an SNS, according to an exemplary embodiment. Referring to FIG. 12,when accessing a registered SNS, the wearable device 100 may attempt tolog in the SNS by inputting an ID and a password of an identified user.

In operation 1210, the wearable device 100 may register SNSauthentication information for the user and a vein image of the user.For example, the SNS authentication information may include the ID andthe password. An SNS authentication number may separately be registeredfor each type of SNS. For example, the wearable device 100 may storedifferent IDs and passwords with respect to a Facebook account and aTwitter account. In addition, the SNS as well as a website forperforming a login may be registered together with the ID and thepassword by using authentication information.

In operation 1220, when accessing the SNS, the wearable device 100 maycapture a vein image of the user wearing the wearable device 100. When aregistered SNS address registered is inputted in a Web browser, thewearable device 100 may control the sensor 110 to capture the veinimage.

In operation 1230, the wearable device 100 may identify the user wearingthe wearable device 100 by comparing the captured vein image with theregistered vein images.

In operation 1240, the wearable device 100 may perform login to the SNSby inputting the SNS authentication information for the identified user.The wearable device 100 may perform the login to the SNS by reading theSNS authentication information registered with respect to the identifieduser from the memory 130.

When accessing the registered SNS, the wearable device 100 may performthe login through vein authentication by using the ID of the userwearing the wearable device 100 even in the absence of a separate input.

FIG. 13 is a diagram illustrating a process by which a wearable device100 displays automatically performs login, according to an exemplaryembodiment. Referring to FIG. 13, when the wearable device 100 accessesa registered SNS, the wearable device 100 may attempt veinauthentication to identify a user.

For example, when a first user wears the wearable device 100 andaccesses FACEBOOK.COM, the wearable device 100 may perform the veinauthentication. In other words, the wearable device 100 may compare acaptured vein image with registered first and second vein images. If thecaptured vein image matches the first vein image, the wearable device100 may determine that the first user is wearing the wearable device100. The wearable device 100 may attempt login by using first SNSinformation for the first user.

FIG. 14 is a diagram illustrating a process by which a wearable device100 automatically performs login, according to an exemplary embodiment.Referring to FIG. 14, when a Web browser accesses Facebook, the wearabledevice 100 may automatically perform login. If, as a result of veinauthentication, a user wearing the wearable device 100 is a first user,the wearable device 100 may perform the login based on first SNSinformation registered with respect to the first user. Since an ID and apassword of the Facebook respectively are AAA and 1111 in the first SNSinformation, the wearable device 100 may input AAA and 1111 in a Website.

The SNS has been described with reference to FIGS. 12 to 14, but thewearable device 100 may also perform the login in the same manner asdescribed above in the case of all Web sites performing a login byinputting the authentication information similar to the case of the SNS.The wearable device 100 may store a vein image, a Web site address, anID, and a password. When the stored Web site address is inputted in theWeb browser, the wearable device 100 may perform the login by inputtingthe ID and the password of the user authenticated through veinauthentication.

FIG. 15 is a flowchart of a method by which a wearable device 100selectively executes a function or an application, according to anexemplary embodiment. Referring to FIG. 15, when a function or anapplication that requires authentication is selected, the wearabledevice 100 may determine through vein authentication whether thefunction or the application should be executed.

In operation 1510, the wearable device 100 may register executionauthority of a user and a vein image of the user. The wearable device100 may register a function or an application available to each user. Inother words, the wearable device 100 may register execution authority ofeach function and each application for each user. For example, thewearable device 100 may store that a first user has authority to executea function C and an application A, and a second user has authority toexecute a function A, a function B, and an application B. Multiplefunctions and applications may be available to a particular user, justas multiple users may have authority to access a particular function orapplication.

In operation 1520, when the function or the application is selected, thewearable device 100 may capture a vein image of the user wearing thewearable device 100.

In operation 1530, the wearable device 100 may identify the user wearingthe wearable device 100 by comparing the captured vein image with theregistered vein images.

In operation 1540, if the identified user has the execution authority,the wearable device 100 may execute the function or the application. Forexample, when the first user wears the wearable device 100 and theapplication C is executed, the wearable device 100 may determine whetherthe first user has the authority to execute the application C, and thewearable device 100 may execute the application C only when the firstuser has the authority to execute the application C. When the first userno authority to execute the application C, the wearable device 100 mayprovide feedback to the user indicating that the application C may notbe executed because he does not have the authority.

Therefore, through vein authentication, the wearable device 100 mayexecute the function or the application only when the user having theexecution authority wears the wearable device 100.

FIG. 16 is a flowchart of a method by which a wearable device 100automatically performs payment with a credit card, according to anexemplary embodiment. Referring to FIG. 16, at the time of payment witha credit card, the wearable device 100 may perform the payment byinputting card information of an identified user through veinauthentication.

In operation 1610, the wearable device 100 may register a vein image ofa user and credit card information of the user. For example, the creditcard information may include a card number, an expiration date, apassword, etc. Any user may register a plurality of pieces of creditcard information.

In operation 1620, at the time of the payment with the credit card, thewearable device 100 may capture a vein image of the user wearing thewearable device 100. When an input of the credit card information in aWeb browser is displayed, the wearable device 100 may control the sensor110 to capture the vein image. The wearable device 100 may determinethrough the card number, the expiration date, or the like, that thepayment with the credit card is performed.

In operation 1630, the wearable device 100 may identify the user wearingthe wearable device 100 by comparing the captured vein image with theregistered vein images.

In operation 1640, the wearable device 100 may perform the payment byusing the credit card information registered with respect to theidentified user. The performing of the payment by the wearable device100 may include inputting the registered credit card information, orinputting the credit card information and pushing a payment button tocomplete final payment. If there is no credit card informationregistered with respect to the identified user, the wearable device 100may perform no payment. In addition, when there is a plurality of piecesof credit card information registered with respect to the identifieduser, the wearable device 100 may display the plurality of pieces ofregistered credit card information and receive an input from the user toperform the payment by using any one of the plurality of pieces ofcredit card information.

At the time of the payment with the credit card, the wearable device 100may perform the payment by using the credit card information on the userwearing the wearable device 100 even in the absence of a separate input.

FIG. 17 is a diagram illustrating a process by which a wearable device100 performs payment by using registered credit card information,according to an exemplary embodiment. Referring to FIG. 17, the wearabledevice 100 may store first credit card information and second creditcard information and may determine payment credit card informationthrough vein authentication at the time of payment with a credit card.

For example, the memory 130 of the wearable device 100 may store thefirst credit card information, the second card information, and firstand second vein images. The first credit card information may be creditcard information of a first user. The second credit card information maybe credit card information of a second user. The first vein image may bea vein image of the first user. The second vein image may be a veinimage of the second user.

According to an exemplary embodiment, the wearable device 100 mayperform vein authentication at the time of the payment with the creditcard. At the time of the payment with the credit card, the wearabledevice 100 may capture a vein image of the user wearing the wearabledevice 100. The wearable device 100 may compare the captured vein imagewith the registered vein images. In FIG. 17, the wearable device 100 maycompare the captured vein image with the first and second vein images.If the captured image matches the first vein image, the wearable device100 may determine the user wearing the wearable device 100 as the firstuser.

Accordingly, the wearable device 100 may perform the payment by usingthe first credit card information of the first user. The first creditcard information may indicate a card company A, a card number of1234-5678, and an expiration date of March, 2017. Therefore, thewearable device 100 may perform the payment by inputting the card numberand the expiration date in a Web browser.

FIG. 18 is a diagram of a payment screen according to an exemplaryembodiment. Referring to FIG. 18, a wearable device 100 may input creditcard information in the payment screen.

The payment screen may include spaces in which a card number and anexpiration date are inputted. The wearable device 100 may input a cardnumber of first credit card information in the space in which the cardnumber is inputted. The wearable device 100 may input an expiration dateof the first credit card information in the space in which theexpiration date is inputted.

In FIG. 18, only the card number and expiration date are shown asinputs, but additional information necessary for payment with a creditcard may be registered and inputted.

FIG. 19 is a flowchart of a method by which a wearable device 100provides an advertisement, according to an exemplary embodiment.Referring to FIG. 19, the wearable device 100 may provide anadvertisement related to interest information of a user.

In operation 1910, the wearable device 100 may register the interestinformation of the user and a vein image of the user. The interestinformation may include a category in which the user wants to acquireinformation. For example, the interest information may includecategories such as exercise, a vehicle, or travel. In addition, theinterest information may be a brand, an enterprise, or the like, thatmay be preferred by the user.

In operation 1920, the wearable device 100 may determine theadvertisement related to the interest information. The wearable device100 may search for the advertisement by using the registered interestinformation. For example, when the travel is registered as the interestinformation of the user, the wearable device 100 may search for anadvertisement including domestic travel or overseas travel information.When the vehicle is registered as the interest information on the user,the wearable device 100 may search for an advertisement of a newlyreleased vehicle.

In operation 1930, the wearable device 100 may identify the user wearingthe wearable device 100 by comparing the captured vein image with theregistered vein images.

In operation 1940, the wearable device 100 may provide the advertisementrelated to the interest information of the identified user. The wearabledevice 100 may display the advertisement in the display unit 120.

Accordingly, the wearable device 100 may provide the advertisement inwhich the user wearing the wearable device 100 is interested, throughvein authentication.

FIG. 20 is a diagram illustrating a process by which a wearable device100 registers interest information, according to an exemplaryembodiment. Referring to FIG. 20, the wearable device 100 may storeinterest information and a vein image for each user.

First interest information may be interest information registered by afirst user. Second interest information may be interest informationregistered by a second user. The first interest information may includea game, exercise, a vehicle, or the like. The second interestinformation may include clothes, cosmetics, travel, or the like.

A first vein image may be a vein image of the first user. A second veinimage may be a vein image of the second user.

The wearable device 100 may register the first interest information andthe first vein image with respect to the first user. The wearable device100 may register the second interest information and the second veinimage with respect to the second user.

When the user wears the wearable device 100, the wearable device 100 maycapture a vein image. The wearable device 100 may compare the capturedvein image with the registered first and second vein images. When thecaptured vein image matches the first vein image, the wearable device100 may determine an advertisement to be provided to the user based onthe first interest information. The advertisement determined by thewearable device 100 may vary according to a time and a location.

FIG. 21 is a flowchart of a method by which a wearable device 100transmits data, according to an exemplary embodiment. Referring to FIG.21, when transmitting data, the wearable device 100 may transmit thedata only when a user has transmission authority.

In operation 2110, the wearable device 100 may register datatransmission authority of the user and a vein image of the user. Thedata transmission authority may indicate a transmission-available datatype and data volume for each user.

In operation 2120, when transmitting the data, the wearable device 100may control the sensor 110 to capture a vein image of the user wearingthe wearable device 100. When the user transmits the data to the outsideof the wearable device 100, the wearable device 100 may capture the veinimage. When the user transmits the data to external electronic devices,the wearable device 100 may capture the vein image and perform veinauthentication before the data is transmitted.

In operation 2130, the wearable device 100 may identify the user wearingthe wearable device 100 by comparing the captured vein image with theregistered vein images.

In operation 2140, when the identified user has the appropriate datatransmission authority, the wearable device 100 may transmit the data.The wearable device 100 may confirm the data transmission authority ofthe identified user. The wearable device 100 may determine based on theconfirmed data transmission authority whether to currently transmit thedata. When a type of the data to be currently transmitted is a type inwhich the user is not authorized to transmit, or a volume of the data tobe currently transmitted is greater than a volume in which the user isauthorized to transmit, the wearable device 100 may display the message“No Data Transmission” on a display unit 120 and may transmit no data.

In other words, the wearable device 100 may determine through veinauthentication whether to transmit the data, based on the datatransmission authority of the user wearing the wearable device 100.

FIG. 22 is a flowchart of a method by which a wearable device 100 isconnected to other devices, according to an exemplary embodiment.Referring to FIG. 22, at the time of a connection to other devices, thewearable device 100 may attempt to connect to other devices by usingconnection information.

In operation 2210, the wearable device 100 may register a vein image ofa user and connection information about other devices. The connectioninformation may include a connection target, a password, etc.

In operation 2220, at the time of the connection to other devices, thewearable device 100 may control the sensor 110 to capture a vein imageof a user wearing the wearable device 100. The connecting to otherdevices may include connecting the wearable device 100 to other devices,and automatically connecting the wearable device 100 to other deviceswhen the wearable device 100 approaches other devices, according to aninput of the user.

In operation 2230, the wearable device 100 may identify the user wearingthe wearable device 100 by comparing the captured vein image with sregistered vein images.

In operation 2240, the wearable device 100 may attempt to connect toother devices by using connection information registered with respect tothe identified user. The wearable device 100 may confirm the connectioninformation registered with respect to the identified user. The wearabledevice 100 may determine based on the confirmed connection informationwhether to attempt to connect to other devices.

The connection information may include a connection device list.Therefore, the wearable device 100 may attempt to connect only todevices included in the connection information. When a device, whichattempts to connect to the wearable device 100, is not included in theconnection information, the wearable device 100 may not attempt toconnect to the device.

The wearable device 100 may attempt to connect to other devices by usinga password included in the connection information. When a peripheraldevice, to which the wearable device 100 attempts to connect, requires apassword, the wearable device 100 may transmit the password included inthe connection information of the user to the peripheral device. Whenthe wearable device 100 may not be connected to the peripheral device,the wearable device 100 may display a message indicating no connectionon the display unit 120.

FIG. 23 is a diagram illustrating a process by which a wearable device100 displays a vein authentication procedure, according to an exemplaryembodiment. Referring to FIG. 23, while the wearable device 100 performsvein authentication, the wearable device 100 may display the message “Inthe process of performing authentication” on the display unit 120.

The case of using a smart watch has been described with reference toFIG. 23, but the message “In the process of performing authentication”may also be displayed on smart glasses.

When a user wears both the smart watch and the smart glasses, the veinauthentication may be performed in the smart watch and the message maybe displayed on the smart glass. In one or more exemplary embodiments,the message may be displayed on the smart watch and iris authenticationmay be performed in the smart glasses.

The wearable device 100 may display the message indicating theauthentication process. In other words, the wearable device 100 maydisplay, on the display unit 120, the message indicating that thewearable device 100 is in the process of performing the authenticationand the message indicating whether the wearable device 100 is in theprocess of performing the vein authentication or the irisauthentication. In addition, the wearable device 100 may display acapturing angle with respect to a vein or an iris and may change thecapturing angle according to a user input.

According to an exemplary embodiment, the wearable device 100 maydisplay a process of generating a vein image. For example, the wearabledevice 100 may display, on the display unit 120, a process of capturingthe vein image and generating the vein image. The wearable device 100may provide an image of cross-comparing the captured vein image with aregistered vein image.

According to an exemplary embodiment, the wearable device 100 maydisplay a process of generating the iris image. For example, thewearable device 100 may display, on the display unit 120, a process ofcapturing the iris image and generating the iris image.

According to an exemplary embodiment, the wearable device 100 maydisplay a process of measuring a pulse. For example, the wearable device100 may display, on the display unit 120, a process of capturing thepulse and extracting pulse characteristics.

According to an exemplary embodiment, the wearable device 100 mayprovide feedback to the user at the time of authentication success orauthentication failure. The authentication success may represent theexistence of a registered vein image, a registered iris image, and aregistered pulse respectively matching with the captured vein image, thecaptured iris image, and the measured pulse. For example, at the time ofthe authentication success, the wearable device 100 may provide avibration or a ringtone and may display, on the display unit 120, themessage indicating the authentication success.

The wearable device 100 may log in a mail account of the user throughthe vein authentication. As illustrated in FIG. 23, when the userselects a Mail icon, the wearable device 100 may perform the veinauthentication and may log in the mail account of the user wearing thewearable device 100 by inputting a registered ID and a registeredpassword with respect to the identified user.

FIG. 24 is a diagram illustrating a process by which a wearable device100 displays an authentication region, according to an exemplaryembodiment. Referring to FIG. 24, when performing vein authentication,the wearable device 100 may display the authentication region 2410capturing a vein image.

As illustrated in FIG. 24, the wearable device 100 may display anauthentication region 2410 by using a laser or an LED. When performingthe vein authentication, the wearable device 100 may display theauthentication region 2410 in order to notify that a vein image in anyregion of the user wearing the wearable device 100 is captured.

FIG. 25 is a diagram of a sensor arrangement of a wearable device 100according to an exemplary embodiment. For example, the wearable device100 may include a sensor 110 on a side surface thereof, which mayinclude at least one light source 111 and at least one camera 112.

In the case of a smart watch, the sensor 110 may be disposed on a sidesurface of the smart watch to capture a vein image of the back of a handof a user wearing the smart watch. The smart watch may capture the veinimage of the back of a user's hand or an image of a shape of a user'sfinger to perform authentication.

FIG. 26 is a diagram of a sensor arrangement of a wearable device 100according to an exemplary embodiment. For example, the wearable device100 may include a sensor 110 on a front surface thereof, which mayinclude at least one light source 111 and at least one camera 112.

In the case of a smart watch, the sensor 110 may be disposed on a frontsurface of the smart watch to capture an image of a body of a userwearing the smart watch. For example, the smart watch may capture a veinimage of the back or the palm of the hand opposite of the hand wearingthe smart watch. In addition, the smart watch may capture an iris imageof the user by using the sensor 110 disposed on the front surfacethereof to perform iris authentication.

Two light sources 111 and one camera 112 are described with reference toFIGS. 25 and 26, but the number of the light sources 111 and the cameras112 is not limited thereto. FIGS. 25 and 26 illustrate that the camera112 is disposed between the light sources 111, however the positions ofthe camera 112 and the light sources 111 are not limited to thisconfiguration. In addition, the camera 112 or the light sources 111 maybe arranged in an array form.

The wearable device according to one or more exemplary embodiments mayprovide a function and an application suitable for the user wearing thewearable device.

The wearable device according to one or more exemplary embodiments maygrant authority to the user through vein authentication.

The wearable device according to one or more exemplary embodiments mayinclude a processor, a memory configured to store and execute programdata, a permanent storage unit such as a disc drive, a communicationport configured to communicate with external devices, and a userinterface such as a touch panel, a key, or a button. Methods, which arerealized by a software module or algorithm, are computer-readable codesor program commands executable on the processor. The methods may bestored computer-readable recording mediums. Examples of thecomputer-readable recording mediums may include a magnetic storagemedium (for example, a read-only memory (ROM), a random-access memory(RAM), a floppy disk, or a hard disk) and an optically readable medium(for example, a CD-ROM or a digital versatile disc (DVD)). Thecomputer-readable recording mediums may be distributed in computersystems connected to each other through a network. Codes, which arereadable by a computer through a distribution method, may be stored andexecuted in the computer-readable recording mediums. Thecomputer-readable recording mediums may be readable by the computer, maybe stored in the memory, and may be processed in the processor.

One or more exemplary embodiments may be represented by functional blockconfigurations and various processing operations. The functional blockconfigurations may be realized by a plurality of hardware and/orsoftware configurations. For example, one or more exemplary embodimentsmay employ direct circuit configurations, such as a memory, processing,logic, and a look-up table, capable of executing various functions by acontrol of at least one microprocessor or other control devices. In thesimilar manner that elements may be executed by software programming orsoftware elements, one or more exemplary embodiments may be realized bya programming or scripting language such as C, C++, Java, or anassembler, including a various of algorithm realized by a datastructure, processes, routines, or combinations of other programmingconfigurations. Functional aspects may be realized by algorithm executedin one or more processors. In addition, one or more exemplaryembodiments may employ an existing art for an electronic environmentsetting, a signal processing, and/or a data processing. The terms“mechanism”, “element”, “means”, and “configuration” may widely be usedand are not limited to mechanical and physical configurations. Theaforementioned terms may include means of a series of routines ofsoftware in conjunction with a processor or the like.

For conciseness, descriptions of conventional electronic configurations,control systems, software and other functional aspects of the systemsmay be omitted above. Furthermore, connections of lines between elementsillustrated in the drawings or connection members are merely examples offunctional connections and/or physical or circuit connections. In actualdevices, the connections of the lines and the connection members may beimplemented with various replaceable and/or additional functionalconnections, physical connections, or circuit connections. Moreover,unless an element is mentioned as specific terms such as “essential” or“important”, the element may be an element not necessarily required forcarrying out the inventive concepts.

The use of the term “the” or a similar definite term in thespecification (in particular, in the claims) may correspond to both thesingular and the plural. In addition, if a range is disclosed in theexemplary embodiments, exemplary embodiments to which individual valuesbelonging to the range are applied may be included (if there is nodisclosure opposite to this), and this is the same as if each of theindividual values forming the range is disclosed.

For steps forming the methods according to the inventive concepts, if anorder is not clearly disclosed or if there is no disclosure opposed tothe clear order, the steps may be performed in any appropriate order.The inventive concepts are not necessarily limited to the disclosedorder of the steps. The use of all illustrations or illustrative terms(for example, and the like, etc.) in the exemplary embodiments is todescribe the exemplary embodiments in detail, and the scope of theinventive concepts is not limited due to the illustrations orillustrative terms unless they are limited by the claims. In addition,it should be understood by those of ordinary skill in the art thatvarious modifications, combinations, and changes may be made accordingto design conditions and factors within the scope of the attached claimsor the equivalents.

It should be understood that exemplary embodiments described hereinshould be considered in a descriptive sense only and not for purposes oflimitation. Descriptions of features and/or aspects within eachexemplary embodiment should typically be considered as available forother similar features or aspects in other exemplary embodiments.

While one or more exemplary embodiments have been described withreference to the figures, it should be understood by those of ordinaryskill in the art that various changes in form and details may be madewithout departing from the spirit and scope as defined by the followingclaims.

What is claimed is:
 1. A wearable device comprising: a display; a sensorconfigured to obtain a biometric information of a user; a memoryconfigured to store at least one instruction; and at least one processorconfigured to execute the at least one instruction to: based on an eventrelated to executing an application, identify execution of biometricauthentication associated with the application; based on theidentification, display a message indicating information correspondingto the biometric authentication to be performed in the wearable device;obtain, by the sensor, the biometric information of the user wearing thewearable device; identify authority using the obtained biometricinformation and registered biometric information stored in the memory;and display, by the display, a screen associated with the executedapplication based on the identified authority.
 2. The wearable device ofclaim 1, wherein the application is an application in which the user ispredesignated.
 3. The wearable device of claim 1, wherein the messagecomprises a type of the biometric authentication.
 4. The wearable deviceof claim 1, wherein the message comprises a capturing angle of thesensor with respect to the user.
 5. The wearable device of claim 4, theat least one processor is further configured to execute the at least oneinstruction to: receive a user input; and modify the capturing angle ofthe sensor in response to the user input.
 6. The wearable device ofclaim 1, wherein the biometric authentication comprises at least one ofvein authentication or iris authentication.
 7. The wearable device ofclaim 1, the at least one processor is further configured to execute theat least one instruction to: display a process of capturing andgenerating at least one of image based on the biometric information. 8.The wearable device of claim 7, the at least one processor is furtherconfigured to execute the at least one instruction to: display an imageof cross-comparing the image based on the biometric information with aimage based on the registered biometric information.
 9. The wearabledevice of claim 1, wherein the event comprises receiving a user input,by an input unit, in order to execute the application.
 10. The wearabledevice of claim 1, the at least one processor is further configured toexecute the at least one instruction to: display, on a body of the user,an authentication region using a light module.
 11. A method of operatinga wearable device, the method comprising: based on an event related toexecuting an application, identifying execution of biometricauthentication associated with the application; based on theidentification, displaying a message indicating informationcorresponding to the biometric authentication to be performed in thewearable device; obtaining, by a sensor, the biometric information of auser wearing the wearable device; identifying authority using theobtained biometric information and registered biometric informationstored in a memory; and displaying, a screen associated with theexecuted application based on the identified authority.
 12. The methodof claim 11, wherein the application is an application in which the useris predesignated.
 13. The method of claim 11, wherein the messagecomprises a type of the biometric authentication.
 14. The method ofclaim 11, wherein the message comprises a capturing angle of the sensorwith respect to the user.
 15. The method of claim 14, furthercomprising: receiving a user input; and modifying the capturing angle ofthe sensor in response to the user input.
 16. The method of claim 11,wherein the biometric authentication comprises at least one of veinauthentication or iris authentication.
 17. The method of claim 11,further comprising displaying a process of capturing and generating atleast one of image based on the biometric information.
 18. The method ofclaim 17, further comprising displaying an image of cross-comparing theimage based on the biometric information with an image based on theregistered biometric information.
 19. The method of claim 11, whereinthe event comprises receiving a user input, by an input unit, in orderto execute the application.
 20. The method of claim 11, furthercomprising displaying, on a body of the user, an authentication regionusing a light module.